Methods and systems for social shopping on a network-based marketplace

ABSTRACT

Methods and systems are provided for social shopping on a network-based marketplace. The system receives a selection, over a network, at a social shopping platform. The selection identifies a request from a user in a first community of users and is associated with a listing describing an item for sale. The social shopping platform includes multiple network-based marketplaces respectively associated with communities. The communities include the first community of users being associated with a first network-based marketplace. The system identifies the first network-based marketplace based on the request. The first network-based marketplace is used by the first community of users for transacting items of a single domain. Finally, the system updates a user reputation score based on the activity associated with the first network-based marketplace and presents second user interface information, over the network, including the listing.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/162,691, filed Oct. 17, 2018, which is a continuation of U.S.application Ser. No. 15/639,841, filed Jun. 30, 2017, which is acontinuation of U.S. application Ser. No. 13/906,129, filed May 30,2013, which is a continuation of U.S. application Ser. No. 13/569,039,filed Aug. 7, 2012, now U.S. Pat. No. 8,515,832, which is a continuationof U.S. application Ser. No. 11/860,791, filed Sep. 25, 2007, now U.S.Pat. No. 8,244,599, that claims the benefit of U.S. ProvisionalApplication Ser. No. 60/904,337, filed Feb. 28, 2007 and U.S.Provisional Application Ser. No. 60/952,831, filed Jul. 30, 2007 all ofwhich are incorporated by reference in their entirety.

FIELD

The present application relates generally to the technical field of dataprocessing.

BACKGROUND

Applications available on the Internet have progressed from facilitatinga medium of information delivery to a venue for sales and more recentlyto a platform for social networking. Online market places such asAmazon.com and eBay.com are examples of online sellers. Similarly,mySpace.com and Facebook.com are examples of social networking. Merginga venue for sales with a social network platform presents challenges.

BRIEF DESCRIPTION OF THE DRAWINGS

The present application is illustrated by way of example and notlimitation in the figures of the accompanying drawings, in which likereferences indicate similar elements and in which:

FIG. 1 is a network diagram depicting a system, according to one exampleembodiment, having a client-server architecture;

FIG. 2 is a block diagram illustrating marketplace and paymentapplications, according to an embodiment;

FIG. 3 is a block diagram illustrating reputation applications,according to an embodiment;

FIG. 4 is a block diagram illustrating social shopping information,according to an embodiment, stored on a database;

FIG. 5 is a block diagram illustrating network-based marketplaceinformation, according to an embodiment;

FIG. 6 is a block diagram illustrating an activity table, according toan embodiment;

FIG. 7 is a block diagram illustrating a listings table, according to anembodiment,

FIG. 8 is a block diagram illustrating a component table, according toan embodiment;

FIG. 9 is a block diagram illustrating an user table, according to anembodiment;

FIG. 10 is a block diagram illustrating listing activity information,according to an embodiment;

FIG. 11 is a block diagram illustrating component activity information,according to an embodiment:

FIG. 12 is a block diagram illustrating user activity information,according to an embodiment;

FIG. 13 is a flow chart illustrating a method, according to anembodiment, to receive a request for an activity associated with alisting;

FIG. 14 is a flow chart illustrating a method, according to anembodiment, to receive a request for an activity associated with acomponent;

FIG. 15 is a flow chart illustrating a method, according to anembodiment, to receive a request for an activity associated with a user;

FIG. 16-17 are diagrams illustrating interfaces, according to anembodiment; and

FIG. 18 is a block diagram of a machine, according to an exampleembodiment, including instructions to perform any one or more of themethodologies described herein.

DETAILED DESCRIPTION

Methods and system for social shopping on a network-based marketplaceare described. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the present application. It will be evident,however, to one skilled in the art that the present application may bepracticed without these specific details.

Platform Architecture

FIG. 1 is a network diagram depicting a system 10, according to oneexemplary embodiment of the present application, having a client-serverarchitecture. A commerce platform, in the exemplary form of a socialshopping platform 12, provides server-side functionality, via a network14 (e.g., the Internet) to one or more clients. FIG. 1 illustrates, forexample, a web client 16 such as the INTERNET EXPLORER offered byMICROSOFT CORPORATION of Redmond, Wash., and a programmatic client 18executing on respective client machines 20 and 22. The social shoppingplatform 12 hosts one or more network-based marketplaces that arerespectively established, customized, and maintained by a community ofusers to achieve a social shopping experience. For example, a communityof users may establish a network-based marketplace for social networkingand online sales of Star Trek goods or services. The community of usersmay further customize the network-based marketplace for Star Treklistings of goods or services by selecting a custom graphical appearance(e.g., a skin) for the interfaces of the network-based marketplace,selecting a set of graphical rankings (e.g., Kirk, Spock, Bones, Scotty,Klingon, etc. that correspond to user reputation scores, selecting anicon that appears on the interfaces to graphically represent thecommunity or some other customization. The community of users mayfurther maintain the network-based marketplace by contributingcomponents (e.g., a meetup application that enables users to arrange anoff-line meeting time and place) to the network-based marketplace thatmay be accessed from the network-based marketplace, contributinglistings to a community auction page on the network-based marketplace,voting up or down (e.g., components, listings, etc.), commenting (e.g.,components, listings, etc.), referring community members, providing helpto community members or other such maintenance. The above describednetwork-based marketplace further includes a reputation system toencourage behaviors that are positive for the community and discouragenegative behaviors. Such a reputation system may, in one embodiment,include providing reputation scores that are visible to the community oninterfaces to provide incentives for the community. For example,providing reputation scores may include listing reputation scores foreach of the listings, component reputation scores for each of thecomponents contributed by a user, and user reputation scores for each ofthe users. Further, users may interact with listings, components andother users such that the reputation score of the user is based on therespective reputation scores of the listings, components and other usersand vice versa.

Turning specifically to the social shopping platform 12, an applicationprogram interface (API) server 24 and a web server 26 are coupled to,and provide programmatic and web interfaces respectively to, one or moreapplication servers 28. The application servers 28 host one or moremarketplace applications 30 and payment applications 32. The applicationservers 28 are, in turn, shown to be coupled to one or more databaseservers 34 that facilitate access to one or more databases 36.

The marketplace applications 30 provide a number of marketplacefunctions and services to users that access one or more of thenetwork-based marketplaces. The payment applications 32 likewise providea number of payment services and functions to users. The paymentapplications 32 may enable one user to pay another user. In addition,the payment applications 32 may allow users to qualify for, andaccumulate, value (e.g., in a commercial currency, such as the U.S.dollar, or a proprietary currency, such as “points”) in accounts, andthen later to redeem the accumulated value for products (e.g., goods orservices) that are made available via the marketplace applications 30.The payment applications 32 may, for example, be embodied as PAYPAL®sevices for processing electronic payment to and from others, an onlineservice offered by EBAY of San Jose, Calif. While the marketplace andpayment applications 30 and 32 are shown in FIG. 1 to both form part ofthe social shopping platform 12, it will be appreciated that, inalternative embodiments of the present application, the paymentapplications 32 may form part of a payment service that is separate anddistinct from the social shopping platform 12.

Further, while the system 10 shown in FIG. 1 employs a client-serverarchitecture, the present application is of course not limited to suchan architecture, and could equally well find application in adistributed, or peer-to-peer, architecture system. The variousmarketplace and payment applications 30 and 32 could also be implementedas standalone software programs, which do not necessarily havenetworking capabilities.

The web client 16, it will be appreciated, accesses the variousmarketplace and payment applications 30 and 32 via the web interfacesupported by the web server 26. Similarly, the programmatic client 18accesses the various services and functions provided by the marketplaceand payment applications 30 and 32 via the programmatic interfaceprovided by the API server 24. The programmatic client 18 may, forexample, be a seller application (e.g., the TURBOLISTER™ applicationdeveloped by EBAY, INC., of San Jose, Calif.) to enable sellers toauthor and manage listings on the social shopping platform 12 in anoff-line manner, and to perform batch-mode communications between theprogrammatic client 18 and the social shopping platform 12.

FIG. 1 also illustrates a third party application 38, executing on athird party machine 40, as having programmatic access to the socialshopping platform 12 via the programmatic interface provided by the APIserver 24. For example, a third party application 38 that is hosted onthe third party machine 40 may provide listings in response to a requestfor listings (e.g., Star Trek listings) from the social shoppingplatform 12. The third party website may, for example, be embodied asthe WORLDS ONLINE MARKETPLACE® service hosted by EBAY, INC. of San Jose,Calif.

Marketplace Applications

FIG. 2 is a block diagram illustrating multiple marketplace and paymentapplications 30, 32 that, in one exemplary embodiment of the presentapplication, are provided as part of the social shopping platform 12.The social shopping platform 12 may provide a number of listing andprice-setting mechanisms whereby a seller may list goods or services forsale, a buyer can express interest in or indicate a desire to purchasesuch goods or services, and a price can be set for a transactionpertaining to the goods or services. To this end, the marketplaceapplications 30 are shown to include one or more auction applications 44which support auction-format listing and price setting mechanisms (e.g.,English, Dutch, Vickrey, Chinese, Double, Reverse auctions etc.). Thevarious auction applications 44 may also provide a number of features insupport of such auction-format listings, such as a reserve price featurewhereby a seller may specify a reserve price in connection with alisting and a proxy-bidding feature whereby a bidder may invokeautomated proxy bidding.

A number of fixed-price applications 46 support fixed-price listingformats (e.g., the traditional classified advertisement-type listing ora catalogue listing) and buyout-type listings. Specifically, buyout-typelistings (e.g., including the BUY IT NOW™ (BIN) technology developed byeBay Inc., of San Jose, Calif.) may be offered in conjunction with anauction-format listing, and allow a buyer to purchase goods or services,which are also being offered for sale via an auction, for a fixed-pricethat is typically higher than the starting price of the auction.

Ping applications 48, according to example embodiment, may be used toenable real time communication between users and between a user and thesocial shopping platform 12. A ping may be a text message to anotheruser. The message may be a request to communicate off the ping system onanother platform. The ping system may also be used by the socialshopping platform 12 to send an alert to a user. In one embodiment, analert may include a success message or a failure message responsive toan action by an user. In one embodiment an alert may be multicasted tousers of a particular network-based marketplace (e.g., community) orbroadcasted to all users on the social shopping platform 12. In oneembodiment, the ping system may deliver a ping in a square container inthe lower right corner of an interface that appears on a browser. In oneembodiment, the ping system may use an alpha transparency fade effect asa ping transitions in and out of the container. In one embodiment, pingalerts may be stacked. For example, a ping that is received may bedisplayed on the bottom of a stack of previously displayed pings.

Reputation applications 50 maintain listing reputation scores, componentreputation scores, and user reputation scores, as previously described.The reputation applications 50 may operate to process requests that arereceived from users and update reputation scores accordingly. Forexample, the reputation applications 50 may process a request from auser to perform an activity associated with a listing a component, oranother user. The reputation applications 50 may update a database basedon the requested activity and update the appropriate reputation scores.For example, a user may request that a thumbs up vote be cast for alisting. In response, the reputation applications 50 may store the votein a database entry for the listing and in a database entry for theuser. The thumbs up vote may contribute to improving the reputationscore associated with the listing because a member of the communityapproved of the listing. Further, the thumbs up vote may contribute toimproving the reputation score for the user because the user has helpedto establish the value of the listing to the community. In addition, thereputation applications 50 may use the reputation score of the listingto update the reputation score of the user and the reputation score ofthe user to update the reputation score of the listing. Accordingly, auser with a relatively high reputation score may have a positiveinfluence on a relatively low reputation score of a listing. Conversely,the relatively high reputation score of the user may be negativelyinfluenced by the relatively low reputation score of the listing.Likewise, the reputation applications 50 perform similar processing fora request from a user for an activity associated with a component thatis utilized on the network-based marketplace and for a request from auser for an activity with another user on the network-based marketplace.Accordingly, the reputation applications 50 allow users of the communityto establish, build and maintain user reputation scores, which may bemade available and published to other users of the community. Otherusers may then reference such a reputation for the purposes of assessingcredibility, trustworthiness, and contributions that are consistent withthe values of the community.

Customization applications 52 may allow users of the network-basedmarketplace to contribute user interface elements that are used topersonalize the user interfaces of the network-based marketplace and tocontribute applications that provide services for the users of thenetwork-based marketplace. For example, the customization applications52 may be utilized by the community of users to contribute and userinterface elements including a community icon user interface element,skin user interface elements, or ranking user interface elements. Acommunity icon user interface element may consistently appear on userinterfaces of the network-based marketplace.

Skin user interface elements may be applied to the user interfaces ofthe network-based marketplace to communicate a custom graphicalappearance. Consistent application of the skin may result in apresentation of user interfaces with a look and feel that uniquelycharacterizes the community. In one embodiment, the skin user interfaceelements may include background images, background colors, headerimages, fonts, text size, text color, and more. In one embodiment,cascading style sheets (CSS), may be used to provide the describedfunctionality in a Web based environment.

Ranking user interface elements may be a set of user interface elementswith each element corresponding to a discrete rank or level (e.g.,1-10), as previously described. For example, a set of user interfaceelements may be downloaded by a user of the community from a remote siteand the rank of each of the user interface elements (e.g., Kirk=toprank) may be determined according to vote by the community. Accordingly,a user interface element with a particular rank may be associated withuser based the user reputation score of the user. For example, thereputation score of the user may be determined to fall within a range ofuser reputation scores associated with the rank. Different ranks may beassociated with the same user in different network-based marketplaces(e.g., different communities). An user interface element correspondingto a rank and associated with a particular user in a community enablesother users in the community to quickly identify the value of the userto the community.

The customization applications 52 further may allow users of thenetwork-based marketplace to contribute applications that provide aservice for the users of the network-based marketplace. For example, auser may select a service that enables users of the community toschedule off-line meetings. In one embodiment, a user may select theapplication MEETUP, an online service that brings groups togetheroffline offered by MEETUP.COM of New York, N.Y.

Listing applications 54 may be used by the network-based marketplace todetermine whether to a acquire a particular listing from a third partymachine 40 (e.g., eBay), sort the order of appearance of the listings ona main auction interface on the network-based marketplace, and purgelistings from the main auction interface on the network-basedmarketplace. The listing applications 54 may acquire, sort, and purgelistings according to relevance information, reputation information, anda recency information. The relevance information may be provided byusers of the network-based marketplace and may include keywords (e.g,“Star”, “Trek”, and “Memorabilia”) that are selected according to thevotes of the users of the community. The listing reputation informationmay include a listing reputation score as described later. The recencyinformation includes the time remaining in an auction of the listing onthe third party machine 40. The relevance information, listingreputation information and recency information may be respectivelyweighted to influence a determination of whether to acquire a particularlisting from the third party machine 40.

Navigation of the social shopping platform may be facilitated by one ormore navigation applications 56. For example, a search applicationenables key word searches of listings published via the network-basedmarketplace. In addition, the navigation applications 56 enable users toaccess various services offered by the network-based marketplace. Forexample, the navigation applications 56 applications enable users toaccess a wish list, news, reviews, guides, blogs, videos, a communityauction interface, a main auction interface, a user profile interface,the ping system, community auctions, a community icon feature, acommunity skin feature, a ranking system, and a reputation calculator.Various other navigation applications 52 may be provided to supplementthe search and browsing applications.

The scratch pad applications 60 enable dragging and dropping of objectsto and from a scratch pad that appears on a user interface. The scratchpad may be a halfway point for transporting an object (e.g., listing,component, etc.). In one embodiment, the scratch pad may operate as acontainer for multiple objects. Further, the scratch pad applications 60may transform an image of an object into a space efficientrepresentation.

The voting applications 62 enable the users of the community to castvotes and determine an outcome of a community vote. For example, thevoting applications 62 may process votes in favor of or opposed to alisting or a component (e.g., a feature, skin, ranking, a communityicon, an application that provides a service to the community, etc.).Further, the voting applications 62 may determine the outcome of a vote.For example, the voting applications may determine the outcome of athumbs up or thumbs down vote for a component such as a community icon.

The community auctions applications 64 may be used by users of thecommunity to acquire particular listings from the third party machine 40for auction on a community auction interface on the network-basedmarketplace.

The comment applications 66 may be used by users of the community toenter comments for listings. The comment applications 66 may include thecomments on interfaces that are used to view the listings.

The processing applications 68 may receive information from the webinterface or the programmatic interface and invoke the appropriateapplications, as described above. For example, the processingapplications 68 may receive a request from a user to vote in favor of alisting. In response to receiving the request, the processingapplication may invoke the voting applications 62 to record the vote forthe listing and the reputation applications 50 to update the appropriateuser reputation score and listing reputation score.

FIG. 3 is a block diagram illustrating reputation applications 50,according to an embodiment. The reputation applications include areceiving module 70 and a reputation module 72. The receiving module 70may receive a request to perform an activity from a client machine 20,22. The receiving module 70 uses the request to determine the type ofactivity and an activity constant associated with the activity. Forexample, the activity may be received from a user and associated with alisting, a component, or another user. The activity constant may be usedto weight or scale the effect of the activity on an update of areputation score. The reputation module 72 updates reputation scores.For example, the reputation module 72 may update a listing reputationscore, a component reputation score or a user reputation score.

FIG. 4 is a block diagram illustrating a social shopping information 74,according to an embodiment, stored on database(s) 36. The socialshopping information 74 includes a systems table 76 and one or morenetwork-based marketplace information 78 entries. The systems table 76includes information for the social shopping platform 12. Eachnetwork-based marketplace information 78 entry may include informationfor a specific network-based marketplace. Specifically, each networknetwork-based marketplace information 78 may include a network-basedmarketplace identifier 80 and a domain 82. The network-based marketplaceidentifier 80 uniquely identifies a particular network-basedmarketplace. The domain 82 (e.g., Star Trek, Star Wars, etc.) mayprovide a user recognizable identity for the network-based marketplace.In one embodiment, the domain 82 may correspond to one or morecategories on third party machine 40 (e.g., eBay).

Data Structures

FIG. 5 is a high-level entity-relationship diagram, illustrating varioustables included in a network-based marketplace information 78 entry. Thenetwork-based marketplace information 78 may be maintained within thedatabases 36, and are utilized by and support a specific network-basedmarketplace (e.g., Star Trek). A user table 92 contains a record foreach registered user of the network-based marketplace, and may includeidentifier, address and financial instrument information pertaining toeach such registered user. A user may, it will be appreciated, operateas a seller, a buyer, or both, within the network-based marketplace. Inone exemplary embodiment of the present application, a buyer may be auser that is able to buy or bid on listings that are offered for sale bythe network-based marketplace.

The network-based marketplace information 78 also includes a listingstable 94 in which are maintained listing records for goods and servicesthat are available to be, or have been, transacted via the network-basedmarketplace. Each listing record within the listings table 94 mayfurthermore be linked to one or more user records within the user table92, so as to associate a seller and one or more actual or potentialbuyers with each listings record. The listings table 94 may furtherstore information for a listing reputation score for each of therespective listings.

A transaction table 96 contains a record for each transaction (e.g., apurchase transaction) pertaining to listings for which records existwithin the listings table 94.

Bid records within a bids table 100 each relate to a bid received at thesocial shopping platform 12 in connection with an auction-format listingsupported by an auction application 44. One or more attributes tables106 record attribute information pertaining to listings for whichrecords exist within the listings table 94. Considering only a singleexample of such an attribute, the attributes tables 106 may indicate acurrency attribute associated with a particular listing, the currencyattribute identifying the currency of a price for the relevant listingas specified by a seller. A components table 110 may store userinterface elements that may be used to generate interfaces for thenetwork-based marketplace and store linkage information to applicationsthat provide services for users of the community. In addition, thecomponents table 110 may further store information for a componentreputation score for each of the respective components. The commenttable 102 may store comments that have been entered by users of thecommunity for listings and components. The activity table 120 may storeactivity constants that may be associated with activities that may berequest by a user. For example, a user may request an activityassociated with a listing, a component, or another user.

FIG. 6 is a block diagram illustrating an activity table 120, accordingto an embodiment. The activity table 120 is used by the receiving module70 to associate activity constants 130 to requests for activities. Theactivity constant 130 is used by the reputation module 72 to provide aweight to an activity in updating a reputation score. For example,activities for a listing may include commenting on the listing, biddingon the listing, and submitting a winning bid for the listing withrespective activity constants being 1, 2, and 3. Accordingly, in oneembodiment, the activity of submitting a winning bid may contributegreater weight to the listing reputation score than the other mentionedactivities. The activity table 120 includes listing information 106,component information 108, and user information 126. The listinginformation 122 includes an activity identifier 128 that is used toassociate an activity constant 130 to an activity for a listing. Thecomponent information 122 and the user information 124 likewise includeactivity identifiers 128 and activity constants 130 that correspond tocomponent and user activities.

FIG. 7 is a block diagram illustrating a listings table 94, according toan embodiment. The listing table 94 includes a listing 200 entry foreach listing on the network-based marketplace. Each listing 200, inaddition to other information not illustrated, is shown to include userrating information 202, vote information 204, user activity information206, sale information 208, comment information 201 that are utilized bythe reputation module 72 to update a listing reputation score 212 forthe listing 200. The user rating information 202 may include a rating ofthe seller of the listing 200. For example, the listing 200 may havebeen retrieved from a third party machine 40 (e.g., eBay) that maintainsa user rating for each of the users. In one embodiment, the sellerrating may be an value that may range from zero to ten that is used tocommunicate a reputation of the user. The vote information 204 mayrecord thumbs-up votes and thumbs-down votes from the users of thecommunity expressing their approval or disapproval of the listing 200.The user activity information 206 may be used to update the listingreputation score 212 based on user reputation scores. The user activityinformation 206 may include activities that are associated with thelisting and requested by a user. For example, an activity of a userrequesting a thumbs-up vote for the listing may be recorded as useractivity information 206. Accordingly, the user reputation score of theuser may be used to update the listing reputation score. Associated witheach activity may be a user identifier 214 and an activity identifier128. The user identifier 214 may be used to identify the user and theactivity identifier 128 may be used to identify the activity and toassociate an activity constant 101 with the activity. The saleinformation 208 may include the number of bids received for the listing.The comment information 210 may record comments from the users of thecommunity for the listing 200.

FIG. 8 is a block diagram illustrating an component table 110, accordingto an embodiment. The component table 110 includes a component 218 entryfor each component on the network-based marketplace. For example, acomponent 218 entry may correspond to a community icon user interfaceelement, a set of skin user interface elements, a ranking user interfaceelements, or an application that provides a service. Each component 218,in addition to other information not illustrated, is shown to includevote information 204, user activity information 206, comment information201 that are utilized by the reputation module 72 to update a componentreputation score 220 for the component 218. The user activityinformation 206 may be used to update the component reputation score 220based on user reputation scores. The user activity information 206 mayinclude activities that are associated with the component and requestedby a user. For example, an activity of a user requesting submission ofuser interface icon for a vote by the community may be recorded as useractivity information 206. Accordingly, the user reputation score of theuser may be used to update the component reputation score 220. The useractivity information 206 for the component 218 likewise includes a useridentifier 214 and an activity identifier 128 for each activity.

FIG. 9 is a block diagram illustrating an user table 92, according to anembodiment. The user table 92 includes a user entry 222 for each user onthe network-based marketplace. Each user entry 222, in addition to otherinformation not illustrated, is shown to include user rating information202, community service information 224, cast vote information 226,listing activity information 228, component activity information 230,user activity information 232, posted comment information 234 that areutilized by the reputation module 72 to update a user reputation score220 for the user entry 222. The community service information recordscontributions made by the user to the community. For example, the usermay post a listing for auction, contribute a component (e.g., an iconuser interface element, contribute a rank user interface element,contribute an application that provides a service to the community,etc.), refer new user to the community, provide help to a user in thecommunity or any other quantifiable contribution to the community. Inone embodiment, each of the previously described services for thecommunity may be recorded by incrementing a counter by one. Otherembodiments may use different values. The cast vote information 226 maybe used to record votes cast by the user. For example, the user may castvotes for a listing or a component. The listing activity information 228may be used to update the user reputation score 236 based on listingreputation scores 212. The listing activity information 228 may includeactivities that are requested by the user and associated with a listing200. The component activity information 230 may be used to update theuser reputation score 236 based on component reputation scores 220. Thecomponent activity information 230 may include activities that arerequest by the user and associated with a component 218. The useractivity information 232 may be used to update the user reputation score236 based other user reputation scores 236. The user activityinformation 232 may include activities that are requested by the userand associated with another user.

FIG. 10 is a block diagram illustrating listing activity information228, according to an embodiment. The listing activity information 228may be accessed via a user entry 222 in the user table 92 and is used bythe reputation module 72 to update the corresponding user reputationscore 236 based on listing reputation scores 212. The listing activityinformation 228 includes an entry for each activity requested by theuser for a listing 200. The listing 200 and the corresponding listingreputation score 212 may be identified by the listing identifier 240 andthe activity and a corresponding activity constant 130 may be identifiedby an activity identifier 128.

FIG. 11 is a block diagram illustrating component activity information230, according to an embodiment. The component activity information 230may be accessed via a user entry 222 in the user table 92 and is used bythe reputation module 72 to update the corresponding user reputationscore 236 based on component reputation scores 220. The componentactivity information 230 includes an entry for each activity requestedby a user for a component 218. The component 218 and the associatedcomponent reputation score 220 may be identified by a componentidentifier 231 and the activity may be identified by an activityidentifier 128.

FIG. 12 is a block diagram illustrating user activity information 232,according to an embodiment. The user activity information 232 may beaccessed via a user entry 222 in the user table 92 and is used by thereputation module 72 to update the corresponding user reputation score236 based on other user reputation scores 236. The user activityinformation 232 includes an entry for each activity requested by a userthat is related to a second user. The user reputation score 236 of thesecond user may be identified by a user identifier 214 and the activitymay be identified by an activity identifier 128.

FIG. 13 is a flow chart illustrating a method 250, according to anembodiment, to receive a request for an activity associated with alisting and update reputation scores. Illustrated on the right is anoperation performed by a client machine 20 and illustrated on the leftare operations performed by the application server machine 28. Themethod 250 commences at operation 252 with a user at the client machine20 requesting a thumbs up vote be cast for a listing. For example, theuser may be voting in favor of a listing for a DVD of the Star TrekMovie: The Next Generation. The user may be voting favorably for thelisting because he believes the DVD is appropriate for the site andwould like to see additional listings like the one viewed. In oneembodiment, the request may include an activity identifier 128, alisting identifier 240, a user identifier 214, and a favorable vote.

At operation 254, at the application server machine 28, the processingapplications 68 identify the appropriate network-based marketplace(e.g., Star Trek), invoke voting applications 62 to register the vote,and invokes the receiving module 70 to update the listing 200 and theuser entry 222. The receiving module 79 updates the listing 200 in thelisting table 94 and the user entry 222 in the user table 92. Thereceiving module 79 updates the listing 200 in the listing table 94based on the listing identifier 240 in the request. The receiving module79 updates the user entry 222 in the user table 92 based on the useridentifier in the request.

The receiving module 70 updates the listing 200 by updating the voteinformation 204 (e.g., +1) and adding an entry to the user activityinformation 206. The receiving module 70 adds an entry that includes theappropriate activity constant 130 and the activity identifier 128 fromthe request.

The receiving module 70 updates the user entry 222 by updating the castvote information 226 (e.g., +1) and adding an entry to the listingactivity information 228. The receiving module 70 adds an entry thatincludes the appropriate activity constant 130 the activity identifier128 from the request.

Updating the Listing Reputation Score

At operation 256, the reputation module 72 updates the listingreputation score 212 for the listing 200 that received the vote. In oneembodiment the reputation module 72 may update the listing reputationscore 212 as follows:

LRS=user rating+votes+bids+comments+(SUM_(i-j)[URS_(i) *K _(i)])/N

Where:

LRS=listing reputation score 212user rating=user rating information 202votes=vote information 204bids=sale information 208comments=comment information 210URS=user reputation score 236K=activity constant 130N=number of user reputation scores 236

Accordingly, the listing reputation score 212 may be based on the userrating information 202, the vote information 204, the sale information208, the comment information 210 and the user reputation scores 236 thatmay be respectively scaled with an activity constant 130. The userrating information 202 may include a rating of the seller that postedthe listing. The vote information 204 may include the net votes whichmay be an integer (e.g., positive or negative whole number). The saleinformation 208 may include the number of bids for the listing. Thecomment information 210 may include the number of comments for thelisting.

The user reputation scores 236 may be retrieved from the user table 92according to user identifiers 214 in the user activity information 206in the listing table 94.

Other examples of requests for activities that may be received for thelisting 200 may include contributing a listing for sale, posting acomment for a listing, bidding on a listing, submitting a winning bidfor a listing, and buying a listing.

Updating the User Reputation Score

At operation 258, the reputation module 72 updates the user reputationscore 236 for the user that cast the vote. In one embodiment thereputation module 72 may update the user reputation score 236 asfollows:

URS=user rating+community service+cast votes+(SUM_(i-j)[LRS_(i) *K_(i)])/N _(l)+(SUM_(i-j)[CRS_(i) *K _(i)])/N _(c)+(SUM_(i-j)[URS_(i) *K_(i)])/N _(u)+posted comments

Where:

URS=user reputation score 236user rating=user rating information 202community service=community service information 224cast votes=cast vote information 226LRS=listing reputation score 212CRS=component reputation score 220URS=user reputation score 236K=activity constant 130N_(l)=number of listing reputation scores 212N_(c)=number of component reputation scores 220N_(u)=number of user reputation scores 236posted comments=posted comment information 234

Accordingly, the user reputation score 236 may be based on the userrating information 202, the community service information 224, the castvote information 226, the listing reputation scores 212 that may berespectively scaled with an activity constant 130, the componentreputation scores 220 that may be respectively scaled with an activityconstant 130, the user reputation scores 236 that may be respectivelyscaled with an activity constant 130, and the posted comment information234.

The community service information 224 may include activities where theuser takes some action that may be characterized as serving thecommunity. For example, community service may include contribution of auser interface icon, contribution of a ranking interface element,contribution of an application (e.g., meetup), contribution of a listingto a community auction page or any other contribution that may beconsidered a benefit to the community. In one embodiment, each of thecommunity services may have a value of one and be associated with aconstant that may be used to scale the value.

The listing reputation scores 212, the component reputation scores 220and the user reputation scores 236 may be retrieved respectively via thelisting activity information 228, component activity information 230,and user activity information 232 for the user entry 222 that correspondto the user that requested the activity. The listing reputation scores212 may be retrieved from the listing table 94 according to listingidentifiers 240 in the listing activity information 228 in the usertable 92 for the user that requested the activity. The componentreputation scores 220 may be retrieved from the component table 110according to component identifiers 231 in the component activityinformation 230 in the user table 92 for the user that requested theactivity. The user reputation scores 236 may be retrieved from the usertable 92 according to user identifiers 214 in the user activityinformation 232 in the user table 92 for the user that requested theactivity. In another embodiment, the reputation score for the user entry222 may be updated before the reputation score for the listing 200.

Another embodiment of the above method may not update the listingreputation score 212 and the user reputation score 236 in response toreceiving a request for an activity associated with a listing. Rather,listing reputation scores 212 and user reputation scores 236 may beupdated periodically and asynchronous to receipt of a request for anactivity associated with a listing and update of the appropriate listing200 and user entry 222.

FIG. 14 is a flow chart illustrating a method 260, according to anembodiment, to receive a request for an activity associated with acomponent 218 and update reputation scores. Illustrated on the right isan operation performed by a client machine 20 and illustrated on theleft are operations performed by the application server machine 28. Themethod 260 commences at operation 260 with a user at the client machine20 requesting submission of a user interface icon for evaluation by thecommunity. For example, the user may be uploading a user interface iconof the Star Ship Enterprise. In one embodiment, the request may includean activity identifier 128, a user identifier 214, a componentidentifier 231, and a user interface icon.

At operation 264, at the application server machine 28, the processingapplications 68 may identify the appropriate network-based marketplace(e.g., Star Trek), invoke customization applications 52 to register theuser interface icon in the component table 110, and invoke the receivingmodule 79 to update the component 218 and the user entry 222.

The receiving module 79 receives the request and updates the component218 in the component table 110 and the user entry 222 in the user table92. The receiving module 79 updates the component 218 based on thecomponent identifier 23 in the request. The receiving module 79 updatesthe user entry 222 based on the user identifier 214 in the request.

The receiving module 70 updates the component 218 by adding an entry tothe user activity information 206. The receiving module 70 adds an entrythat includes the appropriate activity constant 130 and the activityidentifier 128 from the request.

The receiving module 70 updates the user entry 222 by updating thecommunity service information 224 (e.g., +1) and by adding an entry tothe component activity information 230. The receiving module 70 adds anentry that includes the appropriate activity constant 130 and theactivity identifier 128 from the request.

Updating the Component Reputation Score

At operation 266, the reputation module 72 updates the componentreputation score 220 for the component 218 that was contributed. In oneembodiment the reputation module 72 may update the component reputationscore 220 as follows:

CRS=votes+comments+(SUM_(i-j)[URS_(i) *K _(i)])/N

Where:

CRS=component reputation score 220votes=vote information 204comments=comment information 210URS=user reputation score 236K=activity constant 130N=number of user reputation scores 236

Accordingly, the component reputation score 220 may be based on the voteinformation 204 and user reputation scores 236 that may be respectivelyscaled with an activity constant 130. The vote information 204 mayinclude the net votes which may be a positive or negative integer. Theuser reputation scores 236 may be retrieved from the user table 92according to user identifiers 214 in the user activity information 206in the component table 110.

Other requests for activities that may be received for the component 218may include voting for or against the component.

Updating the User Reputation Score

At operation 268, the reputation module 72 updates the user reputationscore 236 for the user that requested submission of the user interfaceicon. In one embodiment the reputation module 72 may update the userreputation score 236 as previously described in operation 258. Inanother embodiment, the reputation score for the user entry 222 may beupdated before the reputation score for the component 218.

Another embodiment of the above method may not update the componentreputation score 220 and the user reputation score 236 in response toreceiving a request for an activity associated with a component. Rather,component reputation scores 220 and user reputation scores 236 may beupdated periodically and asynchronous to receipt of a request for anactivity associated with a component and update of the component 218 andthe user entry 222.

FIG. 15 is a flow chart illustrating a method, according to anembodiment, to receive a request for an activity associated with a user22 and update reputation scores. Illustrated on the right is anoperation performed by a client machine 20 and illustrated on the leftare operations performed by the application server machine 28. Themethod 270 commences at operation 272 with a user at the client machine20 requesting help from another user in the community. For example, theuser may be requesting help from John Doe, with a number one ranking. Inone embodiment, the request may include an activity identifier 128, auser identifier 214 for the requesting user, and a user identifier 214for John Doe.

At operation 274, at the application server machine 28, the processingapplications 68 may identify the appropriate network-based marketplace(e.g., Star Trek), invoke ping applications 48 to facilitatecommunications between the requesting user and John Doe, and invoke thereceiving module 79 update user entries 222.

The receiving module 79 receives the request and updates the user entry222 in the user table 92 based the user identifier 214 for therequesting user. In addition the receiving module 79 updates the userentry 222 in the user table 92 based on the user identifier 214 for JohnDoe.

The receiving module 70 updates the user entry 222 for the requestinguser by adding an entry to the user activity information 232. Thereceiving module 70 adds an entry that includes the appropriate activityconstant 130 and the activity identifier 128 from the request.

The receiving module 70 updates the user entry 222 for John Doe byupdating the community service information 224 (e.g., +1) and by addingan entry to the user activity information 232 The receiving module 70adds an entry that includes the appropriate activity constant 130 and anactivity identifier 128 that indicates John Doe provided help.

Updating the User Reputation Score for the User that Requested Help

At operation 276, the reputation module 72 updates the user reputationscore 236 for the user that requested help. In one embodiment thereputation module 72 may update the user reputation score 236 aspreviously described in operation 258.

Updating the User Reputation Score for the User that Provided Help

At operation 278, the reputation module 72 updates the user reputationscore 236 for the user that provided help. In one embodiment thereputation module 72 may update the user reputation score 236 aspreviously described in operation 258.

Other user activity may include a user referring another user to thecommunity. In another embodiment, the reputation score for the user thatprovided help may be updated before the reputation score for the userthat received help.

Another embodiment of the above method may not update the userreputation scores 236 in response to receiving a request for an activityassociated with a user. Rather, user reputation scores 236 may beupdated periodically and asynchronous to receipt of a request for anactivity associated with a user and update of the user entries 222.

User Interfaces

FIG. 16 is a diagram illustrating an interface 290, according to anembodiment, for a main auction. The interface 290 is shown to include aleft panel, a center panel, and a right panel. The left panel includesuser interface elements that may be selected to access various services.The left panel includes a navigation services user interface element291, a user services user interface element 294, a ping services userinterface element 296, a community auctions user interface element 298,a community icon user interface element 300, a community skin userinterface element 302, a ranking user interface element 304, and areputation calculator user interface element 306. The navigationservices user interface element 291 may be selected to navigate throughinterfaces of the network-based marketplace. The user services userinterface element 294 may be selected to view information about users inthe community. The ping services user interface element 296 may beselected to communicate with another user in the community or tocommunicate with the network-based marketplace. The community auctionsuser interface element 298 may be selected to view a community auctionsinterface that includes listings 200 that have been selected by a memberof a community from a third party machine 40 and to bid on the listings200. The community icon user interface element 300 may be selected tocontribute or vote on a community icon user interface element. Theranking user interface element 304 may be selected to contribute aranking user interface element or to vote on a ranking of ranking userinterface elements. The reputation calculator may be selected tocalculate a listing reputation score 212, a component reputation score220, or a user reputation score 236.

The middle panel of the user interface 290 may include listing userinterface elements 308 for listings 200. The user interface 290 maypresent listings for auction and/or for purchase. The listing userinterface element 308 is for auction and includes a vote count 312 thatcommunicates the net number of votes for the listing 200, user interfaceelements 300 that may be used to cast a vote in favour of or against thelisting, a user interface element 314 to add a comment, and a listingreputation score 212. The middle panel further includes a user interfaceelement 316 to join the community, a user interface element 318 to starta new community, and a user interface element 320 to search for othernetwork-based marketplaces on the social shopping platform 12.

The right panel of the user interface 290 may include a scratch pad 322,a member quicklist 324, and a message box 326. The scratch pad 322 maybe used to annotate a listing 200, a component 218 or other objects onthe network-based marketplace. The member quicklist 324 may be used tocommunicate with a community member and the message box 326 may be usedto send and receive messages.

FIG. 17 is a diagram illustrating an interface 330, according to anembodiment, to display user information. The interface 330 includes aleft middle panel 331 and a right middle panel 332. The left middlepanel 331 presents user information of users that are online (e.g.,signed on to the network-based marketplace) and the right middle panel332 presents user information of users that are offline. The left middlepanel 331 includes user names that may be selected. For example, theuser “Henry Doe” may be selected and is shown to include a ranking userinterface element 336, a user reputation score 236, a listing vote count342, a help provided count 344, a rank 348, a referral count 350, acommunity improvement count 352, and a reviews received count 354.

FIG. 18 shows a diagrammatic representation of machine in the exemplaryform of a computer system 400 within which a set of instructions, forcausing the machine to perform any one or more of the methodologiesdiscussed herein, may be executed. In alternative embodiments, themachine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a server computer,a client computer, a personal computer (PC), a tablet PC, a set-top box(STB), a Personal Digital Assistant (PDA), a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The exemplary computer system 400 includes a processor 402 (e.g., acentral processing unit (CPU) a graphics processing unit (GPU) or both),a main memory 404 and a static memory 406, which communicate with eachother via a bus 408. The computer system 400 may further include a videodisplay unit 410 (e.g., a liquid crystal display (LCD) or a cathode raytube (CRT)). The computer system 400 also includes an alphanumeric inputdevice 412 (e.g., a keyboard), a cursor control device 414 (e.g., amouse), a disk drive unit 416, a signal generation device 418 (e.g., aspeaker) and a network interface device 420.

The disk drive unit 416 includes a machine-readable medium 422 on whichis stored one or more sets of instructions (e.g., software 424)embodying any one or more of the methodologies or functions describedherein. The software 424 may also reside, completely or at leastpartially, within the main memory 404 and/or within the processor 402during execution thereof by the computer system 400, the main memory 404and the processor 402 also constituting machine-readable media.

The software 424 may further be transmitted or received over a network426 via the network interface device 420.

While the machine-readable medium 422 is shown in an exemplaryembodiment to be a single medium, the term “machine-readable medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-readable medium” shall also be taken to include any medium thatis capable of storing, encoding or carrying a set of instructions forexecution by the machine and that cause the machine to perform any oneor more of the methodologies of the present application. The term“machine-readable medium” shall accordingly be taken to include, but notbe limited to, solid-state memories, optical and magnetic media, andcarrier wave signals.

Technology

The methods and systems describe herein may be embodied in any one ormore of the following technologies.

JavaScript

JavaScript is a client side object scripting language used by millionsof Web pages and server applications. With syntax similar to Java andC++, JavaScript may behave as both a procedural and object orientedlanguage. JavaScript is interpreted at run time on the client computerand provides various features to a programmer. Such features includedynamic object construction, function variables, dynamic scriptcreation, and object introspection. JavaScript is commonly used toprovide dynamic interactivity to Web-pages and interact with a pages'DOM hierarchy.

JSON

JSON is an acronym for JavaScript Object Notation, and is a lightweightdata exchange format. Commonly used in AJAX applications as analternative to XML, JSON is human readable and easy to handle in clientside JavaScript. A single function call to eval( ) turns a JSON textstring into a JavaScript object. Such objects may easily be used inJavaScript programming, and this ease of use is what makes JSON a goodchoice for AJAX implementations.

AJAX

AJAX is an acronym for Asynchronous JavaScript and XML but has becomesynonymous for JavaScript applications that use the HTTP Request object.AJAX allows websites to asynchronously load data and inject it into thewebsite without doing a full page reload. Additionally AJAX enablesmultiple asynchronous requests before receiving results. Overall thecapability to retrieve data from the server without refreshing thebrowser page allows separation of data and format and enables greaterecreativity in designing interactive Web applications.

HTML Push/Comet

Comet is similar to AJAX insomuch that it involves asynchronouscommunication between client and server. However, Comet applicationstake this model a step further because a client request is no longerrequired for a server response.

Java NIO

Java NIO is an acronym for Java's New Input Output package, and is a newAPI that provides improved performance in such areas as buffermanagement, scalable network I/O, and file I/O. In particular, an NIOpackage may support non-blocking socket and file I/O. Non-blockingsockets remove the one socket per thread per client limitations oftraditional web server implementations. This allows web servers usingthe NIO package to service multiple clients with a limited number ofsockets and threads

XSL

XSL is a transformation language that may be used to express XML in adifferent format. Similar to CSS, an XSL document describes how toformat an XML hierarchy into HTML or other formats. Generally XSL isused to generate dynamic HTML pages from XML input.

Other Technologies

An example embodiment may be implemented as a dynamic interface and usea set of tools consistent with this platform. In one embodiment, theserver technology may include Tomcat and utilize custom java servletswhich interface with a MYSQL database. In one embodiment, thecommunication protocol used for client server communication may be XML.XML may be transformed on the client side by XSL documents. Theinterface itself may use AJAX to dynamically load content into theinterface without refreshing.

Modules, Components, and Logic

Certain embodiments are described herein as including logic or a numberof modules, components or mechanisms. A module, logic, component ormechanism (herein after collectively referred to as a “module”) may be atangible unit capable of performing certain operations and is configuredor arranged in a certain manner. In example embodiments, one or morecomputer systems (e.g., a standalone, client or server computer system)or one or more components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a “module” that operates to perform certainoperations as described herein.

In various embodiments, a “module” may be implemented mechanically orelectronically. For example, a module may comprise dedicated circuitryor logic that is permanently configured (e.g., within a special-purposeprocessor) to perform certain operations. A module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a modulemechanically, in the dedicated and permanently configured circuitry, orin temporarily configured circuitry (e.g., configured by software) maybe driven by cost and time considerations.

Accordingly, the term “module” should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired) or temporarily configured(e.g., programmed) to operate in a certain manner and/or to performcertain operations described herein. Considering embodiments in whichmodules or components are temporarily configured (e.g., programmed),each of the modules or components need not be configured or instantiatedat any one instance in time. For example, where the modules orcomponents comprise a general-purpose processor configured usingsoftware, the general-purpose processor may be configured as respectivedifferent modules at different times. Software may accordingly configurethe processor to constitute a particular module at one instance of timeand to constitute a different module at a different instance of time.

Modules can provide information to, and receive information from, othermodules. Accordingly, the described modules may be regarded as beingcommunicatively coupled. Where multiple of such modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe modules. In embodiments in which multiple modules are configured orinstantiated at different times, communications between such modules maybe achieved, for example, through the storage and retrieval ofinformation in memory structures to which the multiple modules haveaccess. For example, a one module may perform an operation, and storethe output of that operation in a memory device to which it iscommunicatively coupled. A further module may then, at a later time,access the memory device to retrieve and process the stored output.Modules may also initiate communications with input or output devices,and can operate on a resource (e.g., a collection of information).

Thus, methods and systems for social shopping on a network-basedmarketplace have been described. Although the present subject matter hasbeen described with reference to specific exemplary embodiments, it willbe evident that various modifications and changes may be made to theseembodiments without departing from the broader spirit and scope of thesubject matter. Accordingly, the specification and drawings are to beregarded in an illustrative rather than a restrictive sense.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quicklyascertain the nature of the technical disclosure. It is submitted withthe understanding that it will not be used to interpret or limit thescope or meaning of the claims. In addition, in the foregoing DetailedDescription, it can be seen that various features are grouped togetherin a single embodiment for the purpose of streamlining the disclosure.This method of disclosure is not to be interpreted as reflecting anintention that the claimed embodiments require more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Detailed Description, with each claim standing onits own as a separate embodiment.

1. A system comprising: at least one hardware processor; and anon-transitory computer-readable medium storing executable instructionsthat, when executed, cause the at least one hardware processor toperform operations comprising: receiving, from a user account, a userinput associated with submitting vote information for a listingdescribing an item for sale on an online marketplace, updating areputation score for the user account based on the vote information; andperforming a function of the online marketplace using the updatedreputation score.
 2. The system of claim 1, wherein the item for salecomprises a good or a service.
 3. The system of claim 1, wherein thevote information includes a thumbs-up vote for the listing.
 4. Thesystem of claim 1, wherein the operations further comprise updating thereputation score for the user account based on a reputation score of thelisting.
 5. The system of claim 1, wherein the performing the functioncomprises displaying the updated reputation score in a user interface ona computing device.
 6. The system of claim 1, wherein the performing thefunction comprises: selecting a skin user interface element from among aplurality of different skin user interface elements based on the updatedreputation score; displaying the selected skin user interface element inassociation with the user account in a user interface on a computingdevice.
 7. The system of claim 6, wherein the plurality of differentskin user interface elements comprises background images, backgroundcolors, header images, fonts, text sizes, or text colors.
 8. Acomputer-implemented method comprising: receiving, by a networked systemhaving at least one hardware processor from a user account, a user inputassociated with submitting vote information for a listing describing anitem for sale on an online marketplace; updating, by the networkedsystem, a reputation score for the user account based on the voteinformation; and performing, by the networked system, a function of theonline marketplace using the updated reputation score.
 9. Thecomputer-implemented method of claim 8, wherein the item for salecomprises a good or a service.
 10. The computer-implemented method ofclaim 8, wherein the vote information includes a thumbs-up vote for thelisting.
 11. The computer-implemented method of claim 8, wherein furthercomprising updating the reputation score for the user account based on areputation score of the listing.
 12. The computer-implemented method ofclaim 8, wherein the performing the function comprises displaying theupdated reputation score in a user interface on a computing device. 13.The computer-implemented method of claim 8, wherein the performing thefunction comprises: selecting a skin user interface element from among aplurality of different skin user interface elements based on the updatedreputation score; displaying the selected skin user interface element inassociation with the user account in a user interface on a computingdevice.
 14. The computer-implemented method of claim 13, wherein theplurality of different skin user interface elements comprises backgroundimages, background colors, header images, fonts, text sizes, or textcolors.
 15. A non-transitory computer-readable medium storing executableinstructions that, when executed, cause the at least one hardwareprocessor to perform operations comprising: receiving, from a useraccount, a user input associated with submitting vote information for alisting describing an item for sale on an online marketplace; updating,by the networked system, a reputation score for the user account basedon the vote information; and performing, by the networked system, afunction of the online marketplace using the updated reputation score.16. The non-transitory computer-readable medium of claim 15, wherein theitem for sale comprises a good or a service.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the vote informationincludes a thumbs-up vote for the listing.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the operations furthercomprise updating the reputation score for the user account based on areputation score of the listing.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the performing thefunction comprises displaying the updated reputation score in a userinterface on a computing device.
 20. The non-transitorycomputer-readable medium of claim 15, wherein the performing thefunction comprises: selecting a skin user interface element from among aplurality of different skin user interface elements based on the updatedreputation score; displaying the selected skin user interface element inassociation with the user account in a user interface on a computingdevice.